Add tsvector type support in DML adapter#796
Merged
kvch merged 2 commits intoMay 19, 2026
Merged
Conversation
kvch
approved these changes
May 19, 2026
Collaborator
|
Thank you for this! |
|
Successfully created backport PR for |
kvch
added a commit
that referenced
this pull request
Jun 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fixes #576. Tables with tsvector columns were failing to replicate because the DML adapter didn't have a handler for that type. Added support by converting []byte values to strings before they get used in the copy operation.
Related Issues
#576
Type of Change
Changes Made
Added a case in updateValueForCopy to handle tsvector columns. When a tsvector value comes in as []byte from the WAL, it gets converted to a string. If it's already a string, it passes through unchanged.
Testing
Added two test cases: one for []byte input (which is what the WAL produces) and one for string input to cover both scenarios.
Code Quality